Update gh-action-pypi-publish to v1.14.2 for metadata 2.5 support - #765
Merged
Conversation
The v3.36.0 release failed at the PyPI publish step with "InvalidDistribution: Invalid distribution metadata: '2.5' is not a valid metadata version". Recent hatchling emits core metadata 2.5, which the Twine bundled in gh-action-pypi-publish v1.13.0 does not recognize. v1.14.2 bundles Twine v7, which supports metadata 2.5. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
WHAT
Bump
pypa/gh-action-pypi-publishinrelease.yamlfrom v1.13.0 to v1.14.2 (SHA-pinned).WHY
The v3.36.0 release run failed at the PyPI publish step:
Recent hatchling emits core packaging metadata 2.5, which the Twine bundled in v1.13.0 does not recognize. v1.14.2 bundles Twine v7, which supports metadata 2.5 (per the upstream release notes). Nothing was uploaded to PyPI by the failed run, so re-tagging after this fix will retry the release cleanly.
🤖 Generated with Claude Code